x86: run timers when populating Dom0's P2M table

When booting Dom0 with huge amounts of memory, and/or memory accesses
being sufficiently slow (due to NUMA effects), and the ACPI PM timer
or a high frequency HPET being used, the time it takes to populate the
M2P table may significantly exceed the overflow time of the platform
timer, screwing up time management to the point where Dom0 boot fails.

Signed-off-by: Jan Beulich <jbeulich@novell.com>

diff --git a/xen/arch/x86/domain_build.c b/xen/arch/x86/domain_build.c
index dac49b763389b853fda4000b0d70fdfda48821da..0c35e58b3d19d73edbc1282e12361d72207e699e 100644 (file)
--- a/xen/arch/x86/domain_build.c
+++ b/xen/arch/x86/domain_build.c
@@ -927,6 +927,8 @@ int __init construct_dom0(
         else
             ((unsigned int *)vphysmap_start)[pfn] = mfn;
         set_gpfn_from_mfn(mfn, pfn);
+        if (!(pfn & 0xfffff))
+            process_pending_timers();
     }
     si->first_p2m_pfn = pfn;
     si->nr_p2m_frames = d->tot_pages - count;
@@ -945,6 +947,8 @@ int __init construct_dom0(
 #ifndef NDEBUG
             ++alloc_epfn;
 #endif
+            if (!(pfn & 0xfffff))
+                process_pending_timers();
         }
     }
     BUG_ON(pfn != d->tot_pages);
@@ -965,6 +969,8 @@ int __init construct_dom0(
             set_gpfn_from_mfn(mfn, pfn);
 #undef pfn
             page++; pfn++;
+            if (!(pfn & 0xfffff))
+                process_pending_timers();
         }
     }